addpatch: llvm, ver=22.1.8-2.1 - #974
Merged
Merged
Conversation
wszqkzqk
commented
Aug 7, 2026
wszqkzqk
commented
Member
- Fix <4 x float> to <4 x i64> conversion
- See also: [LoongArch][LASX] Fix fptosi/fptoui from <4 x float> to <4 x i64> llvm/llvm-project#214621
* Fix <4 x float> to <4 x i64> conversion * See also: llvm/llvm-project#214621 Signed-off-by: Zhou Qiankang <wszqkzqk@qq.com>
wangleiat
pushed a commit
to llvm/llvm-project
that referenced
this pull request
Aug 10, 2026
…14621) These were lowered through a 128-bit f32 to i32/u32 conversion followed by a sign/zero extension, which silently clamps any finite input that does not fit in i32/u32 instead of producing the correct 64-bit integer. Convert directly with xvftintrzl.l.s for the signed case. For the unsigned case there is no f32 -> u64 lane conversion in LASX, so widen to f64 first (which is exact) and convert with xvftintrz.lu.d. Both forms use xvpermi.d to move the inputs into the low 64 bits of each 128-bit lane, as required by these lane-wise conversions. Built and verified on Arch Linux for Loong64: lcpu-club/loongarch-packages#974. Both the LLVM side and the Highway test suite that discovered the bug have passed verification. Assisted by Kimi K3 AI agent. Fixes #214605
llvm-upstreamsync Bot
pushed a commit
to qualcomm/cpullvm-toolchain
that referenced
this pull request
Aug 10, 2026
… x i64> (#214621) These were lowered through a 128-bit f32 to i32/u32 conversion followed by a sign/zero extension, which silently clamps any finite input that does not fit in i32/u32 instead of producing the correct 64-bit integer. Convert directly with xvftintrzl.l.s for the signed case. For the unsigned case there is no f32 -> u64 lane conversion in LASX, so widen to f64 first (which is exact) and convert with xvftintrz.lu.d. Both forms use xvpermi.d to move the inputs into the low 64 bits of each 128-bit lane, as required by these lane-wise conversions. Built and verified on Arch Linux for Loong64: lcpu-club/loongarch-packages#974. Both the LLVM side and the Highway test suite that discovered the bug have passed verification. Assisted by Kimi K3 AI agent. Fixes llvm/llvm-project#214605
llvm-sync Bot
pushed a commit
to arm/arm-toolchain
that referenced
this pull request
Aug 10, 2026
… x i64> (#214621) These were lowered through a 128-bit f32 to i32/u32 conversion followed by a sign/zero extension, which silently clamps any finite input that does not fit in i32/u32 instead of producing the correct 64-bit integer. Convert directly with xvftintrzl.l.s for the signed case. For the unsigned case there is no f32 -> u64 lane conversion in LASX, so widen to f64 first (which is exact) and convert with xvftintrz.lu.d. Both forms use xvpermi.d to move the inputs into the low 64 bits of each 128-bit lane, as required by these lane-wise conversions. Built and verified on Arch Linux for Loong64: lcpu-club/loongarch-packages#974. Both the LLVM side and the Highway test suite that discovered the bug have passed verification. Assisted by Kimi K3 AI agent. Fixes llvm/llvm-project#214605
tru
pushed a commit
to llvmbot/llvm-project
that referenced
this pull request
Aug 11, 2026
…vm#214621) These were lowered through a 128-bit f32 to i32/u32 conversion followed by a sign/zero extension, which silently clamps any finite input that does not fit in i32/u32 instead of producing the correct 64-bit integer. Convert directly with xvftintrzl.l.s for the signed case. For the unsigned case there is no f32 -> u64 lane conversion in LASX, so widen to f64 first (which is exact) and convert with xvftintrz.lu.d. Both forms use xvpermi.d to move the inputs into the low 64 bits of each 128-bit lane, as required by these lane-wise conversions. Built and verified on Arch Linux for Loong64: lcpu-club/loongarch-packages#974. Both the LLVM side and the Highway test suite that discovered the bug have passed verification. Assisted by Kimi K3 AI agent. Fixes llvm#214605 (cherry picked from commit 29d7bae)
llvm-upstreamsync Bot
pushed a commit
to qualcomm/cpullvm-toolchain
that referenced
this pull request
Aug 11, 2026
… x i64> (#214621) These were lowered through a 128-bit f32 to i32/u32 conversion followed by a sign/zero extension, which silently clamps any finite input that does not fit in i32/u32 instead of producing the correct 64-bit integer. Convert directly with xvftintrzl.l.s for the signed case. For the unsigned case there is no f32 -> u64 lane conversion in LASX, so widen to f64 first (which is exact) and convert with xvftintrz.lu.d. Both forms use xvpermi.d to move the inputs into the low 64 bits of each 128-bit lane, as required by these lane-wise conversions. Built and verified on Arch Linux for Loong64: lcpu-club/loongarch-packages#974. Both the LLVM side and the Highway test suite that discovered the bug have passed verification. Assisted by Kimi K3 AI agent. Fixes llvm/llvm-project#214605 (cherry picked from commit 29d7bae)
llvm-sync Bot
pushed a commit
to arm/arm-toolchain
that referenced
this pull request
Aug 11, 2026
… x i64> (#214621) These were lowered through a 128-bit f32 to i32/u32 conversion followed by a sign/zero extension, which silently clamps any finite input that does not fit in i32/u32 instead of producing the correct 64-bit integer. Convert directly with xvftintrzl.l.s for the signed case. For the unsigned case there is no f32 -> u64 lane conversion in LASX, so widen to f64 first (which is exact) and convert with xvftintrz.lu.d. Both forms use xvpermi.d to move the inputs into the low 64 bits of each 128-bit lane, as required by these lane-wise conversions. Built and verified on Arch Linux for Loong64: lcpu-club/loongarch-packages#974. Both the LLVM side and the Highway test suite that discovered the bug have passed verification. Assisted by Kimi K3 AI agent. Fixes llvm/llvm-project#214605 (cherry picked from commit 29d7bae)
hulxv
pushed a commit
to llvm/llvm-project
that referenced
this pull request
Aug 12, 2026
…14621) These were lowered through a 128-bit f32 to i32/u32 conversion followed by a sign/zero extension, which silently clamps any finite input that does not fit in i32/u32 instead of producing the correct 64-bit integer. Convert directly with xvftintrzl.l.s for the signed case. For the unsigned case there is no f32 -> u64 lane conversion in LASX, so widen to f64 first (which is exact) and convert with xvftintrz.lu.d. Both forms use xvpermi.d to move the inputs into the low 64 bits of each 128-bit lane, as required by these lane-wise conversions. Built and verified on Arch Linux for Loong64: lcpu-club/loongarch-packages#974. Both the LLVM side and the Highway test suite that discovered the bug have passed verification. Assisted by Kimi K3 AI agent. Fixes #214605
zhangweize9-cyber
pushed a commit
to zhangweize9-cyber/llvm-project
that referenced
this pull request
Aug 16, 2026
…vm#214621) These were lowered through a 128-bit f32 to i32/u32 conversion followed by a sign/zero extension, which silently clamps any finite input that does not fit in i32/u32 instead of producing the correct 64-bit integer. Convert directly with xvftintrzl.l.s for the signed case. For the unsigned case there is no f32 -> u64 lane conversion in LASX, so widen to f64 first (which is exact) and convert with xvftintrz.lu.d. Both forms use xvpermi.d to move the inputs into the low 64 bits of each 128-bit lane, as required by these lane-wise conversions. Built and verified on Arch Linux for Loong64: lcpu-club/loongarch-packages#974. Both the LLVM side and the Highway test suite that discovered the bug have passed verification. Assisted by Kimi K3 AI agent. Fixes llvm#214605
nekoshirro
pushed a commit
to nekoshirro/Alchemist-LLVM
that referenced
this pull request
Aug 30, 2026
…14621) These were lowered through a 128-bit f32 to i32/u32 conversion followed by a sign/zero extension, which silently clamps any finite input that does not fit in i32/u32 instead of producing the correct 64-bit integer. Convert directly with xvftintrzl.l.s for the signed case. For the unsigned case there is no f32 -> u64 lane conversion in LASX, so widen to f64 first (which is exact) and convert with xvftintrz.lu.d. Both forms use xvpermi.d to move the inputs into the low 64 bits of each 128-bit lane, as required by these lane-wise conversions. Built and verified on Arch Linux for Loong64: lcpu-club/loongarch-packages#974. Both the LLVM side and the Highway test suite that discovered the bug have passed verification. Assisted by Kimi K3 AI agent. Fixes llvm/llvm-project#214605 (cherry picked from commit 70cd734) Signed-off-by: Hafidz Muzakky <ais.muzakky@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.